Method and system for magnetic stripe reading using mobile magnetometers

ABSTRACT

In various example embodiments, a system and method for reading magnetic information by a mobile device are presented. In example embodiments, the mobile device comprises a housing having an integrated surface for swiping a magnetic swipe card and a magnetometer positioned within the housing to produce digital magnetometer output signals. The digital magnetometer output signals represent magnetic information derived from the magnetic swipe card and from the Earth&#39;s magnetic fields (or other sources).

RELATED APPLICATION(S)

The present application is a continuation application that claims thebenefit of priority of U.S. Non-Provisional application Ser. No.14/963,639 filed on Dec. 9, 2015, which is hereby incorporated herein byreference in its entirety.

TECHNICAL FIELD

Embodiments of the present disclosure relate generally to dataprocessing and, more particularly, but not by way of limitation, to amethod and system for magnetic stripe reading using mobilemagnetometers.

BACKGROUND

Conventionally, mobile devices such as smart phones may includemagnetometer used as a compass. For example, starting with the iPhone3GS, all iPhones have a built-in magnetometer. The magnetometer in theiPhone is used to find the direction the iPhone is pointed in (e.g., acompass). By knowing the direction the iPhone is pointed in (bymeasuring the direction of the Earth's magnetic field), along withglobal positioning systems (GPS), allows users to use navigation apps ontheir iPhones.

BRIEF DESCRIPTION OF THE DRAWINGS

Various ones of the appended drawings merely illustrate exampleembodiments of the present disclosure and cannot be considered aslimiting its scope.

FIG. 1 is a high level block diagram illustrating a system for readingmagnetic information from a magnetic swipe card and utilizing themagnetic information in various applications, according to some exampleembodiments.

FIG. 2 illustrates an example of a magnetic stripe on a magnetic swipecard used in financial transactions, according to an example embodiment.

FIGS. 3A-3B illustrate a mobile device that includes a magnetometer forreading magnetic information, according to an example embodiment.

FIG. 4 illustrates an electronic compass integrated circuit, accordingto an example embodiment.

FIG. 5 illustrates a flow diagram of a method for detecting magneticcard information from a magnetic card reader, according to an exampleembodiment.

FIG. 6 illustrates a flow diagram of a method for detecting magneticcard information from a magnetic card reader, according to anotherexample embodiment.

FIG. 7 is a block diagram illustrating a networked system, according tosome example embodiments.

FIG. 8 is a block diagram illustrating an example of a softwarearchitecture that may be installed on a machine, according to someexample embodiments.

FIG. 9 illustrates a diagrammatic representation of a machine in theform of a computer system within which a set of instructions may beexecuted for causing the machine to perform any one or more of themethodologies discussed herein, according to an example embodiment.

The headings provided herein are merely for convenience and do notnecessarily affect the scope or meaning of the terms used.

DETAILED DESCRIPTION

The description that follows includes systems, methods, techniques,instruction sequences, and computing machine program products thatembody illustrative embodiments of the disclosure. In the followingdescription, for the purposes of explanation, numerous specific detailsare set forth in order to provide an understanding of variousembodiments of the inventive subject matter. It will be evident,however, to those skilled in the art, that embodiments of the inventivesubject matter may be practiced without these specific details. Ingeneral, well-known instruction instances, protocols, structures, andtechniques are not necessarily shown in detail.

In various example embodiments a mobile device includes a housing havingan integrated surface configured to align magnetic information stored ina magnetic stripe on a magnetic swipe card by moving the magnetic swipecard across the integrated surface of the mobile device for reading themagnetic information. FIG. 2 illustrates an example of a magnetic stripefrom a magnetic swipe card for a financial transaction card (e.g.,credit and banking cards). The magnetic swipe cards can also be used asidentify cards (e.g., driver's licenses), security badges,transportation tickets, loyalty cards, etc. The magnetic stripesrepresent tracks of iron-based magnetic particles that are encoded toorient to one of the magnetic pole positions (e.g., North or South). Theflux reversals that results as the magnetic signal is read across themagnetic stripe results in a code that can be interpreted by a reader(e.g., a magnetometer). Accordingly, the magnetic stripes on themagnetic swipe cards use a strip of magnetic material to store digitaldata. A small amount of data is stored on the strip, may include thecardholder's name, account number, expiration date, etc.

In example embodiments, the mobile device is a smart phone and theintegrated surface is the backside of the smart phone. The integratedsurface is positioned, at least partially, above a magnetometer insidethe mobile device. The magnetometer represents a magnetic reader. Insome embodiments, the built-in magnetometer in a mobile device is usedto pick up the flux reversals in a magnetic stripe as the magnetic swipecard is swiped across the backside of the mobile device.

In further embodiments, the built-in magnetometer may be calibrated topick up the flux reversals in a magnetic stripe as the magnetic swipecard is swiped across the backside of the mobile device. In otherembodiments, the digital magnetometer output signals may be calibratedby a processor executing an algorithm. Calibrations may be used toaccount for various environmental factors such as the Earth's magneticfield, electric currents in the ionosphere, temperature, and hard andsoft iron distortions. For example, to calibrate for the Earth'smagnetic field, the device's location (e.g. via GPS) can be found andused to compare the device's location to the known magnetic strength atthat location on the Earth, measured in Gauss units (this can beconverted to Tesla). Slight variations in the ionosphere can influencethe Earth's magnetic field on the order of 0.2-0.3 mGauss (average).Temperature can also factor into magnetic readings and must also befactored into the algorithm. Hard and soft iron distortions result fromobjects in the magnetic field; distinctions between hard and soft irondistortions pertain to the specific material of the object. In thecontext of a mobile device, the internal components that surround themagnetometer must also be factored into the algorithm and will vary fromdevice to device as their components vary. Secondary distortions canoccur from other objects, like the human body.

In further embodiments, a magnetometer is used to read information bydetecting a direction and strength of magnetic fields from the Earth andmagnetic fields from the magnetic card information for generatingdigital magnetometer output signals. In some embodiments, themagnetometer is an integrated circuit compass chip located within themobile device that may be able detect magnetic fields from a variety ofmagnetic sources, for example magnetic card information from magneticswipe cards as well as the Earth's magnetic fields.

In various embodiments, the magnetometer produces the digitalmagnetometer output signals associated with the magnetic cardinformation and other magnetic sources. In some embodiments, the otherdigital magnetometer output signals represent the digital magnetometeroutput signals associated with the Earth or associated with medicalinformation related to a human body of a person or user. In otherembodiments, a processor within the mobile device performs a filteringfunction for filtering the digital magnetometer output signals derivedfrom various magnetic sources. In various embodiments, the filtering maybe performed based on the magnitude of the digital magnetometer outputsignals. In various embodiments, the magnitude of the digitalmagnetometer output signals are associated with the strength of themagnetic fields detected or measured by the magnetometer. In variousembodiments described, the direction of the magnetic fields may berepresented by x, y, and z directional vectors.

In other embodiments, the magnetometer includes an analog-to-digitalconverter for providing digital magnetometer output signals associatedwith the magnetic card information and digital magnetometer outputsignals associated with the earth, and magnetic sources.

In other example embodiment, the mobile device includes a processor thatreceives the digital magnetometer output signals, and may performfurther processing (e.g., calibrations, filtering, etc.) beforeutilizing the digital magnetometer output signals in variousapplications, such as apps executing on a mobile device. The digitalmagnetometer output signals may be associated with the differentmagnetic sources, for example, the magnetic card information, the Earth,or medical information associated with the human body. In variousembodiments, the processor from the mobile device determines whichdigital magnetometer output signals are to be provided to whichapplication installed and/or executing on the mobile device, or someother computing device. For example, the mobile device may receive somesort of indication to provide the digital magnetometer output signals toa particular application. One indication may be when a particularapplication (e.g., a magnetic swipe card application) is open on themobile device, such that the relevant digital magnetometer outputsignals (e.g., those signals associated with the magnetic cardinformation) are sent to that application by the processor in the mobiledevice.

In some embodiments, the digital magnetometer output signals areassociated with the magnetic card information, and the processor in themobile device is used to decode the magnetic information associated withthe magnetic card information and to make digital signals available to amagnetic swipe card application when the processor of the mobile deviceis executing instructions from the magnetic swipe card application. Inother embodiments, the digital magnetometer output signals areassociated with other magnetic information from other magnetic sources,and the processor in the mobile device is further configured to makethose signals available to other applications when the processor of themobile device is executing instructions from the other applications.Examples of other applications include a compass application that usesthe digital magnetometer output signals associated with the Earth, amedical application (e.g., a blood application or a body fatapplication) that uses the digital magnetometer output signalsassociated with the medical information from a human body.

In other example embodiments, some or all of the components of themagnetic swipe card application may be running on another computingdevice and may access the digital magnetometer output signals associatedwith the magnetic card information.

In a further embodiment, a method of magnetic stripe reading using amobile device is described. The method includes reading magnetic cardinformation by swiping a magnetic stripe on a magnetic swipe card alonga surface of a mobile device positioned partially over a magnetometer.The magnetometer within the mobile device reads the magnetic cardinformation and also detects other magnetic information from othermagnetic sources (e.g., the Earth, human bodies, electronics, or otheritems in the environment). The magnetometer within the mobile devicegenerates digital magnetometer output signals. A processor of a machinedetermines at least some of the digital magnetometer output signalsrepresent encoded magnetic card information and at least some of thedigital magnetometer output signals represent the other magneticinformation detected. A processor of a machine executes at least one ofa magnetic card information application and another magneticapplication. The magnetic card information application utilizes theencoded magnetic card information and the other magnetic applicationutilizes the other magnetic information detected in example embodiments.

In another embodiment, a method of magnetic stripe reading using amobile device is described. A magnetometer included within a mobiledevice detects magnetic information. At least some of the magneticinformation is decoded by a processor of a machine. A processor of amachine filters the magnetic information to determine magnetic cardinformation associated a magnetic card application and Earth's magneticfield information associated with a compass application. In response toinstructions executing on the processor of the machine from the magneticcard application, the magnetic card information is accessed. In responseto instructions executing on the processor of the machine from thecompass application, the Earth's magnetic field information is accessed.

FIG. 1 illustrates a system for reading magnetic information from amagnetic swipe card according to an example embodiment. The system 1000includes a mobile device 1300 communicatively coupled to a networkedsystem 102 via a network 104. The networked system 102 includes one ormore remote servers and associated databases. In example embodiments,the mobile device 1300 may represent a client device 710, as shown inFIG. 7. The networked system 102, the network 104 and the mobile device1300 (represented by the client device 710) are described in furtherdetail in conjunction with the embodiment described in FIG. 7.

A magnetic swipe card 1200 represents a type of card capable of storingdata by modifying the magnetism of tiny iron-based magnetic particles ona band of magnetic material on the card (also referred to as themagnetic stripe or magstripe). The data from the magnetic stripe is readby swiping the magnetic stripe past a magnetic read head. A magnetometer1310 represents an example of a read head, also referred to as a reader.

In the embodiment shown in FIG. 1, a user 1100 has a magnetic swipe card1200 that he or she swipes across a mobile device 1300. For example, themobile device 1300 represents a smart phone that has a back side orsurface that can be used to swipe the magnetic swipe card 1200 by movingthe magnetic swipe card 1200 across the back surface. In variousembodiments, the surface used for swiping is integrated with the mobiledevice 1300, and not an external device (e.g., a dongle) connected viaan earphone jack of a mobile device 1300 or other type of reader. Atleast a portion of the back surface of the user device 1300 ispositioned over a magnetometer 1310 for reading the magnetic cardinformation from the magnet swipe card 1200.

The mobile device 1300 includes a built-in magnetometer 1310 and has avariety of applications installed on the mobile device 1300 (e.g., asshown in FIG. 1) that can use magnetic information encoded in themagnetic swipe card 1200 and other magnetic information sensed by themagnetometer 1310. The other information sensed or detected by themagnetometer 1310 may include, for example, magnetic information relatedto the Earth's magnetic fields, magnetic information related to a useror human body, or magnetic information related to electronic components.

Various magnetometers have different sensitivities and can measure arange of magnetic fields originating from a various magnetic sources.Thus, depending on the sensitivity of the magnetometer within the mobiledevice determines which magnetic fields are detected. Examples of othermagnetic sources and associated strengths (or magnitudes) of theirmagnetic fields include pulsed fields (e.g., 40-60 teslas);electromagnets (e.g., 2-5 teslas); Earth's fields (e.g., between 10⁻⁵ to10⁻⁴ teslas); traffic, appliances, etc. (e.g., between 10⁻⁶ to 10⁻⁵teslas); power transmission lines at 10 meters (e.g., between 10⁻⁸ to10⁻⁷ teslas); human hear signals (e.g., between 10⁻¹⁰ to 10⁻⁹ teslas);optic nerve signals (e.g., between e.g., 10⁻¹² to 10⁻¹¹ teslas); andmuscle impulses and spontaneous brain activity (e.g., in the range of10⁻¹²).

These magnetic fields may be generated by a variety of magnetic sourcessuch as a human body (e.g., a heart and brain of a person, muscleimpulses, and optic nerve signals), a magnet, variouselectrical/electronic appliances including TVs and computers, powertransmission lines, etc. The Earth also has its own magnetic field withits largest at the poles (˜60 000 nanoteslas (nT)) and it is smallest asthe equator (˜30 000 nT). These examples of magnetic signals generatedby a variety of sources, other than the magnetic swipe card 1200, arereferred to as other magnetic information throughout the specification.Various embodiments described throughout the specification, filter themagnetic information such that the magnetic information derived from thedifferent sources can be determined or identified. The digitalmagnetometer output signals that are filtered are then sent to relevantapplications or apps. In other embodiments, calibration is used tocorrect for deviations (caused by magnetic fields from other sources) inthe detected magnetometer signals.

The information detected, sensed or measured by the magnetometer 1310may be used by a number of applications installed on the mobile device1300. As shown in FIG. 1, in an example embodiment, the mobile device1300 may have at least one of the following applications or types ofapplications installed on it: compass applications 1320, magnetic swipecard applications 1330, and other magnetic applications 1340 (e.g.,medical applications). The compass applications may use information fromthe digital magnetometer output signals associated with the Earth'smagnetic field. The magnetic swipe card applications (e.g., paymentapplications, banking applications, security applications, travelapplications, and ticketing applications) may use information from thedigital magnetometer output signals associated with magnetic stripes ona magnetic swipe card. The medical applications may use information inthe digital magnetometer output signals associated with the human body(e.g., heart, brain, blood, muscles, and nerves).

In some examples, the digital magnetometer output signals associatedwith the Earth's magnetic field have magnitudes within a first range;the digital magnetometer output signals associated with magnetic stripeson a magnetic swipe card have magnitudes within a second range; and thedigital magnetometer output signals associated with the human body havemagnitudes within a third range. There may be some overlap with one ormore of the first, second and third ranges. In various embodiment,filtering may be based on the magnitude ranges of the digitalmagnetometer output signals. For example, digital magnetometer outputsignals having a magnitude within a first range may be filtered fromdigital magnetometer output signals having a magnitude within a secondrange.

When executing one of the applications on the mobile device 1300, therelevant information (i.e., derived from the relevant magnetic source)is provided to that application. In various embodiments, a processorfrom the mobiles device determines what information is to be madeaccessible to which application. In some embodiments, the processor mayfilter the digital magnetometer output signals based on the magnitude ofthe signals detected by the magnetometer (also referred to as digitalmagnetometer output signals). In some examples, the magnitude range ofthe signals may be used for filtering. In other embodiments, a processorin another computing device or component may be used to perform thefiltering of the output signals produced by the magnetometer based onthe magnitude of the output signals.

In some embodiments, the networked system 102 includes one or moreremote servers and associated databases. The client applicationsinstalled in the mobile device 1300 may have a corresponding server-sideapplication hosted by the networked system 102. For example, the compassapplications 1620 (corresponding to the compass applications 1320), themagnetic swipe card applications 1630 (corresponding to the magneticswipe card applications 1330), and the other magnetic applications 1640(corresponding to the other magnetic applications 1340) may be hosted bythe networked system 102. In some embodiments the functional componentsof an application may be shared or distributed between the clientapplication and the corresponding server-side application. For example,the mobile device 1300, which includes the magnetometer 1310, may senseand capture the magnetic signals from or more sources, and theprocessing (e.g., filtering, processing, and actions based on thevarious signals) could be performed partially by the networked system102, or partially by the networked system 102.

In one example embodiment, a mobile device comprises a housing having anintegrated surface for swiping a magnetic swipe card; a magnetometer,positioned within the mobile device, for detecting direction andstrength of magnetic fields to read magnetic information and to producedigital magnetometer output signals. The digital magnetometer outputsignals representing magnetic information derived from the magneticswipe card and from the Earth's magnetic fields. Each of the digitalmagnetometer output signals having a magnitude related to the strengthof the detected magnetic fields. The mobile devices comprises a memorydevice for storing instructions and a processor coupled to themagnetometer, when executing the instructions, causes the mobile deviceto: determine at least some of the digital magnetometer output signalsrepresent the magnetic information derived from the magnetic cardinformation; determine at least some of the digital magnetometer outputsignals represent the magnetic information derived from the Earth'smagnetic fields; provide the digital magnetometer output signalsrepresenting the magnetic information derived from the magnetic cardinformation to a magnetic swipe card application for processing; andprovide the digital magnetometer output signals representing themagnetic information derived from the Earth's magnetic information to acompass application for processing.

The mobile device 1300 includes a magnetometer 1310 which is used tomeasure magnetic fields. Generally, a magnetometer includes a sensorthat measures magnetic flux density B (in units of tesla). Magneticfields are considered vector quantities characterized by both strengthand direction. The strength of a magnetic field is measured in units oftesla in the international system of units (SI units), and in gauss inthe centimeter-gram-second system of units (cgs units). 10,000 gauss areequal to one tesla. Measurements of the Earth's magnetic field are oftenquoted in units of nanotesla (nT), also called a gamma. The Earth'smagnetic field can vary from 20,000 to 80,000 nT depending on location,fluctuations in the Earth's magnetic field are on the order of 100 nT,and magnetic field variations due to various magnetic anomalies in thepicotesla (pT) range.

There are two basic types of magnetometer measurements. Vectormagnetometers measure the vector components of a magnetic field. Totalfield magnetometers or scalar magnetometers measure the magnitude of thevector magnetic field. Magnetometers used to study the Earth's magneticfield may express the vector components of the field in terms ofdeclination (the angle between the horizontal component of the fieldvector and magnetic north) and the inclination (the angle between thefield vector and the horizontal surface).

Many smartphones available today contain magnetometers that detectmagnetic information that are provided to applications that serve ascompasses. For example, the magnetometer in the iPhone® (manufactured byApple® Inc.) provides the magnetic field strength along three axis inmicro-teslas (μT) and can be used to find the direction the iPhone® ispointed in. The magnetometers in the iPhone® can also be used to measurethe strength of magnetic fields. In some iPhones®, the magnetometer isimplemented using an AK8973 chip or AK8963 chip (manufactured by AsahiKasei MicroDevices Corp.) to detect magnetic fields using the Halleffect. These chips are 3-axis electronic compass integrated circuits(IC) with high sensitivity Hall sensor technology. Example iPhones® canmeasure magnetic fields up to about 1 T with a precision of about 8 μT(8 micro-teslas).

Magnetic saturation and remanence are two characteristics that determinethe strength (or measurability) of the magnetic information provided bymagnetic swipe card information. The magnetic saturation represents themaximum magnetization a stripe can carry and the point at which itproduces its highest output signal amplitude. The remanence representsthe extent the stripe remains magnetized after having applied thesaturating magnetic field. There is a third characteristic, coercivity,which determines how much magnetic field it takes to erase or overwritea magnetic stripe. Low-coercivity cards are around 300 Oersted (Oed)(30,000 micro-Teslas), while high-coercivity cards are around 4000 Oed(400,000 micro-Teslas). In example embodiments, the coercivity of themagnetic stripes used in cards falls somewhere between 300-4000 Oed.

As described above, a magnetic swipe card 1200 is a type of card capableof storing data by modifying the magnetism of tiny iron-based magneticparticles on a band of magnetic material on the card. FIG. 2 illustratesa magnetic swipe card 1200 according to an example embodiment. Byencoding data on the magnetic stripe, data can be entered into acomputer with a single swipe of the magnetic swipe card 1200. Thedimensions shown in FIG. 2 represent the dimension of an examplefinancial transaction card. The dimensions of an example magnetic swipecard 1200 includes a thickness 203 of 0.030 inches, a height 201 of2.125 inches, and a width 202 of 3.375 inches. Other magnetic swipecards may have different dimensions.

In most magnetic swipe cards (e.g., the magnetic swipe card 1200) iscontained in a plastic-like film. The magnetic stripe 204 is located0.223 inches (5.66 mm) from the edge of the card. The magnetic stripecontains three tracks, each 0.110 inches (2.79 mm) wide. Tracks one andthree are typically recorded at 210 bits per inch (8.27 bits per mm),while track two typically has a recording density of 75 bits per inch(2.95 bits per mm). Each track can either contain 7-bit alphanumericcharacters, or 5-bit numeric characters. Track 1 standards were createdby the airlines industry (IATA). Track 2 standards were created by thebanking industry (ABA). Track 3 standards were created by theThrift-Savings industry.

Currently, there are many standards by the International Organizationfor Standardization and by the International Electrotechnical Commissionreferred to as ISO/IEC standards for magnetic stripe use. The mostcommonly used standards are the ISO/IEC 7810, 7811, 7812 and 7813 seriesof standards. These standards are written for the credit and debit cardmarket and so include information on the embossed characters on thecards as well as the track locations and information on the magneticstripe. ISO/IEC 7811 has six parts with parts two and six specificallyabout low and high coercivity magnetic stripes. These standards includeinformation on the magnetic properties that guarantee that the stripecan be read in a magnetic stripe reader in the U.S.A. as well as inJapan. The ISO/IEC 7811 series of standards define track one as a readonly track with 210 bits per inch and 6 bits plus a parity bit percharacter. This allows for a full alpha-numeric encoding. Track two andthree both use four bits plus a parity bit (number characters plus A toF) only, with track two at 75 bits per inch and track three at 210 bitsper inch. Additionally, three new American National Standards (ANSI)standards that relate to magnetic stripe performance are in progress.These are: (1) Effective Magnetic Parameters of Magnetic Stripes; (2)Suggested Magnetic Parameter Values for Applications; and (3) MagneticStripe Readers and Encoders-Equipment Specifications.

Magnetic stripe technology is used by many people and often on a dailybasis in various industries. The transportation industry often uses thestripe technology for airline tickets and other transportation ortransit tickets. The security industry often uses the magnetic stripetechnology on security badges and security checkpoints. The retailindustry often uses the stripe technology on loyalty cards and rewardcards. The financial industry often uses the stripe technology onfinancial transaction cards (e.g., credit cards, debit cards, and otherbanking cards). Today, financial cards (which generally adhere to the150 standards to ensure read reliability world-wide) and along withtransportation cards constitute the largest users of magnetic swipecards.

Magnetic stripe technology provides an optimal solution to many aspectsof our lives. It is very inexpensive and readily adaptable to manyfunctions. The standardization of high coercivity for the financialmarkets has provided the industry with an extended life. This coupledwith the advent of the security techniques now available means that manyapplications can expect to be using magnetic stripe technology in thefuture.

Examples of cards adhering to these standards include ATM cards, bankcards (credit and debit cards including VISA and MasterCard), giftcards, loyalty cards, driver's licenses, telephone cards, membershipcards, electronic benefit transfer cards (e.g. food stamps), and nearlyany application in which value or secure information is not stored onthe card itself. Many video game and amusement centers now use debitcard systems based on magnetic swipe cards.

FIG. 3A is a block diagram of a mobile device 1300, according to anexample embodiment. In some embodiments, the mobile device 1300 may be asmartphone, and in alternative embodiments, the mobile device 1300 maybe a tablet computer, personal computer, laptop computer, netbook,set-top box, video game console, head-mounted display (HMD) or otherwearable computing device, other types of devices that includes amagnetometer. The mobile device 1300 may include a processor 310, whichmay be any of a variety of different types of commercially availableprocessors suitable for mobile devices (for example, an XScalearchitecture microprocessor, a Microprocessor without InterlockedPipeline Stages (MIPS) architecture processor, or another type ofprocessor). In example embodiments, the processor 310 may be implementedwith one or more central processing units (CPUs), micro-controllers,graphics processing units (GPUs) and/or digital signal processors(DSPs).

A memory 320, such as a Random Access Memory (RAM), a Flash memory, oranother type of memory, is typically accessible to the processor 310.The memory 320 may be adapted to store an operating system (OS) 330, aswell as applications 340. The applications 340 may represent the compassapplications 1320, the magnetic swipe card applications 1330, and othermagnetic applications 1340.

The processor 310 may be coupled, either directly or via appropriateintermediary hardware, to a display 350 and to one or more input/output(I/O) devices 360, such as a keypad, a touch panel sensor, a microphoneand the like. Additionally, the mobile device 1300 may include amagnetometer 1310.

The performance and capabilities of magnetometers (e.g., magnetometer1310) are described through their technical specifications. Majorspecifications include:

-   -   Sample rate is the number of readings given per second. The        inverse is the cycle time in seconds per reading. Sample rate is        important in mobile magnetometers; the sample rate and the        vehicle speed determine the distance between measurements.    -   Bandwidth or bandpass characterizes how well a magnetometer        tracks rapid changes in magnetic field. For magnetometers with        no onboard signal processing, bandwidth is determined by the        Nyquist limit set by sample rate. Modern magnetometers may        perform smoothing or averaging over sequential samples achieving        a lower noise in exchange for lower bandwidth.    -   Resolution is the smallest change in magnetic field the        magnetometer can resolve. A magnetometer should have a        resolution a good deal smaller than the smallest change one        wishes to observe, to avoid quantization errors.    -   Absolute error is the difference between the averaged readings        of a magnetometer in a constant magnetic field and true magnetic        field.    -   Drift is the change in absolute error over time.    -   Thermal, stability is the dependence of the measurement on        temperature. It is given as a temperature coefficient in units        of nT per degree Celsius.    -   Noise is the random fluctuations generated by the magnetometer        sensor or electronics. Noise is given in units of nT/√{square        root over (Hz)}, where frequency component refers to the        bandwidth.    -   Sensitivity is the larger of the noise or the resolution.    -   Heading error is the change in the measurement due to a change        in orientation of the instrument in a constant magnetic field.    -   The dead zone is the angular region of magnetometer orientation        in which the instrument produces poor or no measurements. All        optically pumped, proton-free precession, and Overhauser        magnetometers experience some dead zone effects.    -   Gradient tolerance is the ability of a magnetometer to obtain a        reliable measurement in the presence of a magnetic field        gradient.

Similarly, in some embodiments, the processor 310 may be coupled to atransceiver 370 that interfaces with an antenna 390. The transceiver 370may be configured to both transmit and receive cellular network signals,wireless data signals, or other types of signals via the antenna 390,depending on the nature of the mobile device 1300. In this manner, aconnection between the mobile device 1300 and the network 104 may beestablished. Further, in some configurations, a GPS receiver 380 mayalso make use of the antenna 390 to receive GPS signals.

FIG. 3B illustrates a back view 1320 of the mobile device 1300 accordingto an example embodiment. In various embodiments, the back viewrepresents a back surface of the mobile device 1300 that may be used asa swiping surface for the magnetic swipe card 1200.

FIG. 4 illustrates an electronic compass IC 400 according to an exampleembodiment. In some embodiments the magnetometer 1310 (shown in FIG. 1)may be implemented using an integrated circuit compass chip such as theelectronic compass IC 400 located within the mobile device 1300 (shownin FIG. 1). The electronic compass IC 400 may detect and capturemagnetic signals, and in some embodiments, may perform additionalprocessing of the magnetic sensor signals. The electronic compass IC 400may be implemented using the AK8963 IC which incorporates magneticsensors for detecting terrestrial magnetism in the X-axis, Y-axis, andZ-axis, a sensor driver circuit, a signal amplifier chain, and anarithmetic circuit for processing the magnetic sensor signal from eachsensor. The AK8963 chip includes a wide dynamic measurement range andhigh resolution with lower current consumption. Output data resolution:14-bit (0.6 uT/LSB) and 16-bit (0.15 uT/LSB).

In some embodiments, one or more hardware and/or software componentswithin the electronic compass IC circuit 400 may need to modified (ornew components added) to detect and measure the magnetic fields from thedesired magnetic sources. For example, the sensitivity of the electroniccompass IC circuit 400 may need to be increased to read and process themagnetic card information from a magnetic swipe card or the medicalinformation from a human body.

The electronic compass IC circuit 400 includes a 3-axis Hall sensor 401that includes monolithic Hall elements; a MUX 402 for selecting Hallelements; a chopper SW 403 that performs chopping (i.e., breaking up DCsignals so it can be processed more easily and amplified, increasingstability and accuracy of the signal); a HE-Drive 405 representing amagnetic sensor drive circuit, a pre-amp 404 representing a fixed-gaindifferential amplifier used to amplify the magnetic sensor signal; avoltage reference 407; an integrator & ADC 412 that integrates andamplifies the pre-AMP output and performs analog-to-digital conversion,an interface logic & register 413 that exchanges signals with a CPUusing input/outputs (I/Os) 415; an OSC1 408 generates an operating clockfor sensor measurement; an OSC2 410 generates an operating clock forsequencer; timing control 409 generates a timing signal required forinternal operation from a clock generated by the OSC1 408; a POR 411representing a power on reset circuit; a fuse ROM 414 representing afuse for adjustment; a magnetic source 406 generates a magnetic fieldfor self-test of a magnetic sensor. Various power supply pins 415include pins VSS, VDD and VID. Various input current pins 417 includepins CAD0, CAD1, TRG and TST1. The chopper 403 is an electronic switchthat interrupts a signal under the control of another; and corrects forsignal errors, in this case, resulting from the Hall effect. The I/Os415 include an SDA/SI terminal for receiving input signals and an SOterminal for providing output signals via a digital serial interface(e.g. I²C bus interface).

FIGS. 5-6 illustrates flow diagrams for methods 500-600 implemented invarious embodiments. In some embodiments, additional operations may beadded to each of the methods 500-600, or one or more operations may bedeleted from each of the methods 500-600. In further embodiments, themethods 500-600 or variants of these methods, may be combined. Theoperations performed in the methods 500-600 may be performed by one ormore components or modules within the networked system 102 (e.g.,magnetic reader system 750) or by the mobile device 1300. For example,some of the operations performed by the methods 500-600 may be executedby the magnetic swipe card application 1630 running on the networkedsystem 102, or the magnetic swipe card application 1320 running on themobile device 1300. For example, the reading of the magnetic informationfrom the various magnetic sources may occur at a mobile device, butfurther processing of the signals detected by the magnetometer may beperformed by the mobile device or other computing device (e.g., a remoteserver).

FIG. 5 describes a method 500 for reading and detecting digitalmagnetometer output signals for utilization by various applications,according to example embodiments. The method 500 includes operations510-560. At operation 510, magnetic card information is ready by swipinga magnetic stripe on a magnetic swipe card along a surface of a mobiledevice positioned at least partially over a magnetometer within themobile device.

At operation 520, other magnetic information is detected by themagnetometer within the mobile device from other magnetic sources. Forexample, other magnetic information sensed by a magnetometer (e.g.,magnetometer 1310) may include, for example, magnetic informationrelated to the Earth's magnetic fields, magnetic information related toa user or human body, magnetic information related to electroniccomponents, or magnetic information related to other items in theenvironment.

At operation 530, generating, by a magnetometer within the mobiledevice, digital magnetometer output signals. At operation 540,determining, by a processor of a machine, at least some of the digitalmagnetometer output signals represent encoded magnetic card information.At operation 550, determining, by a processor of a machine, at leastsome of the digital magnetometer output signals represent the othermagnetic information detected. At operation 560, executing, by aprocessor of a machine, at least one of a magnetic card informationapplication utilizing the encoded magnetic card information and anothermagnetic application utilizing the other magnetic information detected.

In other embodiments, the method 500 includes: storing the digitalmagnetometer output signals; accessing, by the processor of the machine,the encoded magnetic card information based on instructions from themagnetic card information application; and accessing, by the processorof the machine, the other magnetic application based on instructionsfrom the other magnetic application.

In another embodiment, the operation of determining at least some of thedigital magnetometer output signals represent encoded magnetic cardinformation includes identifying the encoded magnetic card informationbased on the strength of the magnetic fields generated by magneticstripe on the magnetic swipe card.

In a further embodiment, the operation of determining at least some ofthe digital magnetometer output signals represent the detected othermagnetic information includes identifying the other magnetic informationbased on the strength of the magnetic fields generated by the Earth.

In yet another embodiment, the operation of determining at least some ofthe digital magnetometer output signals represent the detected othermagnetic information includes identifying the other magnetic informationbased on the strength of the magnetic fields generated by a bloodsample.

In an example embodiment, a method for reading and detecting digitalmagnetometer output signals for utilization by various applications,includes the operations of: detecting, by a magnetometer within a mobiledevice, direction and strength of magnetic fields from a magnetic swipecard that were swiped along a surface of the mobile device; detecting,by the magnetometer within the mobile device, direction and strength ofmagnetic fields from an other magnetic source; generating, by themagnetometer within the mobile device, digital magnetometer outputsignals, the digital magnetometer output signals representing magneticinformation derived from the magnetic swipe card and from the othermagnetic source, each of the digital magnetometer output signals havinga magnitude related to the strength of the detected magnetic fields;determining, by a processor of a machine, at least some of the digitalmagnetometer output signals represent the detected magnetic informationderived from the magnetic swipe card; determining, by a processor of amachine, at least some of the digital magnetometer output signalsrepresent the detected magnetic information from the other magneticsource; and executing, by a processor of a machine, at least one of amagnetic card application utilizing the digital magnetometer outputsignals representing the detected magnetic information derived from themagnetic swipe card and an other application utilizing the digitalmagnetometer output signals representing the detected magneticinformation derived the other magnetic source.

FIG. 6 describes a method 600 for detecting digital magnetometer outputsignals for utilization by various applications, according to exampleembodiments. The method 600 includes operations 610-650. At operation610, detecting magnetic information by a magnetometer included within amobile device. At operation 620, decoding, by a processor of a machine,at least some of the magnetic information that was detected to producean output signal.

At operation 630, filtering, by a processor of a machine, the magneticinformation to determine magnetic card information associated a magneticcard application and Earth's magnetic field information associated witha compass application. More specifically, filtering the magneticinformation derived from various sources based on magnitudes of theoutput signals. For example, the magnetic card information has outputsignals with magnitudes within a first range and the Earth's magneticfield information has output signals with magnitudes within a secondrange.

At operation 640, accessing the magnetic card information in response toinstructions executing on the processor of the machine from the magneticcard application. At operation 650 accessing the Earth's magnetic fieldinformation in response to instructions executing on the processor ofthe machine from the compass application.

In another embodiment, the method 600 includes filtering, by theprocessor of the machine, the magnetic information to determine medicalinformation associated with a medical application; and accessing themedical information in response to instructions executing on theprocessor of the machine from a medical application.

In an example embodiment, a method for reading and detecting digitalmagnetometer output signals for utilization by various applications,includes the operations of receiving digital magnetometer output signalscaptured by a mobile device, the digital magnetometer output signalsincluding magnetic information derived from a magnetic swipe card andEarth's magnetic field; filtering the magnetic information to determinewhether the digital magnetometer output signals represents magneticinformation associated with the magnetic swipe card or magneticinformation associated with the Earth's magnetic fields based on amagnitude of the digital magnetometer output signals; providing thedigital magnetometer output signals representing the magneticinformation associated with the magnetic swipe card to a magnetic swipecard application for processing; and providing the digital magnetometeroutput signals representing the magnetic information associated with theEarth's magnetic fields to a compass application for processing.

With reference to FIG. 7, an example embodiment of a high-levelclient-server-based network architecture 700 is shown. A networkedsystem 102, in the example forms of a network-based marketplace orpayment system, provides server-side functionality via a network 104(e.g., the Internet or wide area network (WAN)) to one or more clientdevices 710. FIG. 7 illustrates, for example, a web client 712 (e.g., abrowser, such as the Internet Explorer® browser developed by Microsoft®Corporation of Redmond, Washington State), client application(s) 714,and a programmatic client 716 executing on client device 710.

The client device 710 may comprise, but are not limited to, a mobilephone, or other client devices that include a magnetometer. For example,desktop computer, laptop, portable digital assistants (PDAs), smartphones, tablets, ultra books, netbooks, laptops, multi-processorsystems, microprocessor-based or programmable consumer electronics, gameconsoles, set-top boxes, or any other device that may access thenetworked system 102 may include a magnetometer. In various embodiments,a mobile device, includes one or more devices described above, that hasa magnetometer capable of measuring the strength of magnetic fields froma variety of sources. In some embodiments, the client device 710 maycomprise a display module (not shown) to display information (e.g., inthe form of user interfaces). In further embodiments, the client device710 may include one or more of a magnetometer or other magnetic reader,touch screens, accelerometers, gyroscopes, cameras, microphones, globalpositioning system (GPS) devices, and so forth. The client device 710may be a device of a user that is used to perform a transactioninvolving digital items within the networked system 102. In oneembodiment, the networked system 102 is a network-based marketplace thatresponds to requests for product listings, publishes publicationscomprising item listings of products available on the network-basedmarketplace, and manages payments for these marketplace transactions.One or more users 706 may be a person, a machine, or other means ofinteracting with client device 710. In embodiments, the user 706 is notpart of the network architecture 700, but may interact with the networkarchitecture 700 via client device 710 or another means. For example,one or more portions of network 104 may be an ad hoc network, anintranet, an extranet, a virtual private network (VPN), a local areanetwork (LAN), a wireless LAN (WLAN), a wide area network (WAN), awireless WAN (WWAN), a metropolitan area network (MAN), a portion of theInternet, a portion of the Public Switched Telephone Network (PSTN), acellular telephone network, a wireless network, a Wi-Fi network, a WiMAXnetwork, another type of network, or a combination of two or more suchnetworks.

Each of the client device 710 may include one or more applications (alsoreferred to as “apps”) such as, but not limited to, a web browser,messaging application, electronic mail (email) application, ane-commerce site application (also referred to as a marketplaceapplication), and the like. In some embodiments, if the e-commerce siteapplication is included in a given one of the client device 710, thenthis application is configured to locally provide the user interface andat least some of the functionalities with the application configured tocommunicate with the networked system 102, on an as needed basis, fordata and/or processing capabilities not locally available (e.g., accessto a database of items available for sale, to authenticate a user, toverify a method of payment, etc.). Conversely if the e-commerce siteapplication is not included in the client device 710, the client device710 may use its web browser to access the e-commerce site (or a variantthereof) hosted on the networked system 102.

One or more users 706 may be a person, a machine, or other means ofinteracting with the client device 710. In example embodiments, the user706 is not part of the network architecture 700, but may interact withthe network architecture 700 via the client device 710 or other means.For instance, the user provides input (e.g., touch screen input oralphanumeric input) to the client device 710 and the input iscommunicated to the networked system 102 via the network 104. In thisinstance, the networked system 102, in response to receiving the inputfrom the user, communicates information to the client device 710 via thenetwork 104 to be presented to the user. In this way, the user caninteract with the networked system 102 using the client device 710.

An application program interface (API) server 720 and a web server 722are coupled to, and provide programmatic and web interfaces respectivelyto, one or more application server(s) 740. The application servers 740may host one or more publication systems 742 and payment systems 744,each of which may comprise one or more modules or applications and eachof which may be embodied as hardware, software, firmware, or anycombination thereof. The application servers 740 are, in turn, shown tobe coupled to one or more database server(s) 724 that facilitate accessto one or more information storage repositories or database(s) 726. Inan example embodiment, the database(s) 726 are storage devices thatstore information to be posted (e.g., publications or listings) to thepublication system 720. The database(s) 726 may also store digital iteminformation in accordance with example embodiments.

Additionally, a third party application 732, executing on third partyserver(s) 730, is shown as having programmatic access to the networkedsystem 102 via the programmatic interface provided by the API server720. For example, the third party application 732, utilizing informationretrieved from the networked system 102, supports one or more featuresor functions on a website hosted by the third party. The third partywebsite, for example, provides one or more promotional, marketplace, orpayment functions that are supported by the relevant applications of thenetworked system 102.

The publication systems 742 may provide a number of publicationfunctions and services to users 706 that access the networked system102. The payment systems 744 may likewise provide a number of functionsto perform or facilitate payments and transactions. While thepublication system 742 and payment system 744 are shown in FIG. 7 toboth form part of the networked system 102, it will be appreciated that,in alternative embodiments, each system 742 and 744 may form part of apayment service that is separate and distinct from the networked system102. In some embodiments, the payment systems 744 may form part of thepublication system 742.

The magnetic reader system 750 may provide functionality operable toexecute various applications utilizing information from various magneticsources. In an example embodiment, the onboard processing performedusing the mobile device 1300 (shown in FIG. 1) and the signal captureprocessing is performed by the magnetic reader system 750. For example,the filtering, processing, and actions based on the various signalscould be determined by the application server(s) 740 (the magneticreader system 750), and therefore making the client device 710 more of athin client which is used only for sensing and capturing the signalsfrom the magnetic sources. In other example embodiments, the onboardprocessing and the signal capture processing is performed by the clientdevice 710 (e.g., mobile device 1300).

For example, the magnetic reader system 750 may access the user selecteddata from the databases 726, the third party servers 730, thepublication system 742, and other sources. In some example embodiments,the magnetic reader system 750 may execute some or all of the componentsof at least one of the compass applications 1620, the magnetic swipecard applications 1630, and the other magnetic applications 1640.

In some example embodiments, the magnetic reader system 750 maycommunicate with the publication system(s) 742 and payment system(s)744. For example, when the source of the magnetic information is derivedfrom a financial transaction card, the magnetic reader system 750 maycommunicate with the payment system(s) 744. In other embodiments, whenthe source of the magnetic information is derived from a rewards card ora loyalty card, the magnetic reader system 750 may communicate with thepublication systems 120. In an alternative embodiment, the magneticreader system 750 may be a part of at least one of the publicationsystem 742 and the payment system 744.

Further, while the client-server-based network architecture 700 shown inFIG. 7 employs a client-server architecture, the present inventivesubject matter is of course not limited to such an architecture, andcould equally well find application in a distributed, or peer-to-peer,architecture system, for example. The various publication system 742,payment system 744, and magnetic reader system 750 could also beimplemented as standalone software programs, which do not necessarilyhave networking capabilities.

The web client 712 may access the various publication and paymentsystems 742 and 744 via the web interface supported by the web server722. Similarly, the programmatic client 716 accesses the variousservices and functions provided by the publication and payment systems742 and 744 via the programmatic interface provided by the API server720. The programmatic client 716 may, for example, be a sellerapplication (e.g., the Turbo Lister application developed by eBay® Inc.,of San Jose, Calif.) to enable sellers to author and manage listings onthe networked system 102 in an off-line manner, and to performbatch-mode communications between the programmatic client 716 and thenetworked system 102.

Additionally, a third party application 732, executing on a third partyserver(s) 730, is shown as having programmatic access to the networkedsystem 102 via the programmatic interface provided by the API server720. For example, the third party application 732, utilizing informationretrieved from the networked system 102, may support one or morefeatures or functions on a website hosted by the third party. The thirdparty website may, for example, provide one or more promotional,marketplace, or payment functions that are supported by the relevantapplications of the networked system 102.

Modules, Components, and Logic

Certain embodiments are described herein as including logic or a numberof components, modules, or mechanisms. Modules may constitute eithersoftware modules (e.g., code embodied on a machine-readable medium) orhardware modules. A “hardware module” is a tangible unit capable ofperforming certain operations and may be configured or arranged in acertain physical manner. In various example embodiments, one or morecomputer systems (e.g., a standalone computer system, a client computersystem, or a server computer system) or one or more hardware modules ofa computer system (e.g., a processor or a group of processors) may beconfigured by software (e.g., an application or application portion) asa hardware module that operates to perform certain operations asdescribed herein.

In some embodiments, a hardware module may be implemented mechanically,electronically, or any suitable combination thereof. For example, ahardware module may include dedicated circuitry or logic that ispermanently configured to perform certain operations. For example, ahardware module may be a special-purpose processor, such as aField-Programmable Gate Array (FPGA) or an Application SpecificIntegrated Circuit (ASIC). A hardware module may also includeprogrammable logic or circuitry that is temporarily configured bysoftware to perform certain operations. For example, a hardware modulemay include software executed by a general-purpose processor or otherprogrammable processor. Once configured by such software, hardwaremodules become specific machines (or specific components of a machine)uniquely tailored to perform the configured functions and are no longergeneral-purpose processors. It will be appreciated that the decision toimplement a hardware module mechanically, in dedicated and permanentlyconfigured circuitry, or in temporarily configured circuitry (e.g.,configured by software) may be driven by cost and time considerations.

Accordingly, the phrase “hardware module” should be understood toencompass a tangible entity, be that an entity that is physicallyconstructed, permanently configured (e.g., hardwired), or temporarilyconfigured (e.g., programmed) to operate in a certain manner or toperform certain operations described herein. As used herein,“hardware-implemented module” refers to a hardware module. Consideringembodiments in which hardware modules are temporarily configured (e.g.,programmed), each of the hardware modules need not be configured orinstantiated at any one instance in time. For example, where a hardwaremodule comprises a general-purpose processor configured by software tobecome a special-purpose processor, the general-purpose processor may beconfigured as respectively different special-purpose processors (e.g.,comprising different hardware modules) at different times. Softwareaccordingly configures a particular processor or processors, forexample, to constitute a particular hardware module at one instance oftime and to constitute a different hardware module at a differentinstance of time.

Hardware modules can provide information to, and receive informationfrom, other hardware modules. Accordingly, the described hardwaremodules may be regarded as being communicatively coupled. Where multiplehardware modules exist contemporaneously, communications may be achievedthrough signal transmission (e.g., over appropriate circuits and buses)between or among two or more of the hardware modules. In embodiments inwhich multiple hardware modules are configured or instantiated atdifferent times, communications between such hardware modules may beachieved, for example, through the storage and retrieval of informationin memory structures to which the multiple hardware modules have access.For example, one hardware module may perform an operation and store theoutput of that operation in a memory device to which it iscommunicatively coupled. A further hardware module may then, at a latertime, access the memory device to retrieve and process the storedoutput. Hardware modules may also initiate communications with input oroutput devices, and can operate on a resource (e.g., a collection ofinformation).

The various operations of example methods described herein may beperformed, at least partially, by one or more processors that aretemporarily configured (e.g., by software) or permanently configured toperform the relevant operations. Whether temporarily or permanentlyconfigured, such processors may constitute processor-implemented modulesthat operate to perform one or more operations or functions describedherein. As used herein, “processor-implemented module” refers to ahardware module implemented using one or more processors.

Similarly, the methods described herein may be at least partiallyprocessor-implemented, with a particular processor or processors beingan example of hardware. For example, at least some of the operations ofa method may be performed by one or more processors orprocessor-implemented modules. Moreover, the one or more processors mayalso operate to support performance of the relevant operations in a“cloud computing” environment or as a “software as a service” (SaaS).For example, at least some of the operations may be performed by a groupof computers (as examples of machines including processors), with theseoperations being accessible via a network (e.g., the Internet) and viaone or more appropriate interfaces (e.g., an Application ProgramInterface (API)).

The performance of certain of the operations may be distributed amongthe processors, not only residing within a single machine, but deployedacross a number of machines. In some example embodiments, the processorsor processor-implemented modules may be located in a single geographiclocation (e.g., within a home environment, an office environment, or aserver farm). In other example embodiments, the processors orprocessor-implemented modules may be distributed across a number ofgeographic locations.

Machine and Software Architecture

The modules, methods, applications and so forth described in conjunctionwith FIGS. 5-6 are implemented in some embodiments in the context of amachine and an associated software architecture. The sections belowdescribe representative software architecture(s) and machine (e.g.,hardware) architecture that are suitable for use with the disclosedembodiments.

Software architectures are used in conjunction with hardwarearchitectures to create devices and machines tailored to particularpurposes. For example, a particular hardware architecture coupled with aparticular software architecture will create a mobile device, such as amobile phone, tablet device, or so forth. A slightly different hardwareand software architecture may yield a smart device for use in the“internet of things,” While yet another combination produces a servercomputer for use within a cloud computing architecture. Not allcombinations of such software and hardware architectures are presentedhere as those of skill in the art can readily understand how toimplement the invention in different contexts from the disclosurecontained herein.

Software Architecture

FIG. 8 is a block diagram 800 illustrating a representative softwarearchitecture 802, which may be used in conjunction with various hardwarearchitectures herein described. FIG. 8 is merely a non-limiting exampleof a software architecture and it will be appreciated that many otherarchitectures may be implemented to facilitate the functionalitydescribed herein. The software architecture 802 may be executing onhardware such as machine 1000 of FIG. 9 that includes, among otherthings, processors 1010, memory 1030, and I/O components 1050. Arepresentative hardware layer 904 is illustrated and can represent, forexample, the machine 1000 of FIG. 9. The representative hardware layer904 comprises one or more processing units 906 having associatedexecutable instructions 908. Executable instructions 908 represent theexecutable instructions of the software architecture 802, includingimplementation of the methods, modules and so forth of FIGS. 6-7.Hardware layer 904 also includes memory and/or storage modules 910,which also have executable instructions 908. Hardware layer 904 may alsocomprise other hardware as indicated by 912 which represents any otherhardware of the hardware layer 904, such as the other hardwareillustrated as part of machine 1000.

In the example architecture of FIG. 8, the software 802 may beconceptualized as a stack of layers where each layer provides particularfunctionality. For example, the software 802 may include layers such asan operating system 814, libraries 816, frameworks/middleware 818,applications 820 and presentation layer 822. Operationally, theapplications 820 and/or other components within the layers may invokeapplication programming interface (API) calls 824 through the softwarestack and receive a response, returned values, and so forth illustratedas messages 826 in response to the API calls 824. The layers illustratedare representative in nature and not all software architectures have alllayers. For example, some mobile or special purpose operating systemsmay not provide a frameworks/middleware layer 818, while others mayprovide such a layer. Other software architectures may includeadditional or different layers.

The operating system 814 may manage hardware resources and providecommon services. The operating system 814 may include, for example, akernel 828, services 830, and drivers 832. The kernel 828 may act as anabstraction layer between the hardware and the other software layers.For example, the kernel 828 may be responsible for memory management,processor management (e.g., scheduling), component management,networking, security settings, and so on. The services 830 may provideother common services for the other software layers. The drivers 832 maybe responsible for controlling or interfacing with the underlyinghardware. For instance, the drivers 832 may include display drivers,camera drivers, Bluetooth®® drivers, flash memory drivers, serialcommunication drivers (e.g., Universal Serial Bus (USB) drivers), Wi-Fi®drivers, audio drivers, power management drivers, and so forth dependingon the hardware configuration.

The libraries 816 may provide a common infrastructure that may beutilized by the applications 820 and/or other components and/or layers.The libraries 816 typically provide functionality that allows othersoftware modules to perform tasks in an easier fashion than to interfacedirectly with the underlying operating system 814 functionality (e.g.,kernel 828, services 830 and/or drivers 832). The libraries 816 mayinclude system 834 libraries (e.g., C standard library) that may providefunctions such as memory allocation functions, string manipulationfunctions, mathematic functions, and the like. In addition, thelibraries 816 may include API libraries 836 such as media libraries(e.g., libraries to support presentation and manipulation of variousmedia format such as MPREG4, H.264, MP3, AAC, AMR, JPG, PNG), graphicslibraries (e.g., an OpenGL framework that may be used to render 2D and3D in a graphic content on a display), database libraries (e.g., SQLitethat may provide various relational database functions), web libraries(e.g., WebKit that may provide web browsing functionality), and thelike. The libraries 816 may also include a wide variety of otherlibraries 838 to provide many other APIs to the applications 820 andother software components/modules.

The frameworks 818 (also sometimes referred to as middleware) mayprovide a higher-level common infrastructure that may be utilized by theapplications 820 and/or other software components/modules. For example,the frameworks 818 may provide various graphic user interface (GUI)functions, high-level resource management, high-level location services,and so forth. The frameworks 818 may provide a broad spectrum of otherAPIs that may be utilized by the applications 820 and/or other softwarecomponents/modules, some of which may be specific to a particularoperating system or platform.

The applications 820 includes built-in applications 840 and/or thirdparty applications 842. Examples of representative built-in applications840 may include, but are not limited to, a contacts application, abrowser application, a book reader application, a location application,a media application, a messaging application, and/or a game application.In some embodiments, a compass application and/or a magnetic readerapplication may be included within the built-in applications 840 and/orthird party applications 842. In some embodiments, the magnetic readerapplication may perform the operations described in methods 500 and 600,shown in FIG. 5 and FIG. 6, respectively. Third party applications 842may include any of the built in applications as well as a broadassortment of other applications. In a specific example, the third partyapplication 842 (e.g., an application developed using the Android™ oriOS™ software development kit (SDK) by an entity other than the vendorof the particular platform) may be mobile software running on a mobileoperating system such as iOS™, Android™, Windows® Phone, or other mobileoperating systems. In this example, the third party application 842 mayinvoke the API calls 824 provided by the mobile operating system such asoperating system 814 to facilitate functionality described herein.Examples of other applications included within the applications 820include the compass applications 1320, the magnetic swipe cardapplications 1330, and the other magnetic card applications 1340. Inother embodiments, the corresponding mobile applications (e.g., thecompass applications 1320, the magnetic swipe card applications 1330,and the other magnetic card applications 1340) installed and executableon the mobile device 710 may be included in the client applications 714.In further embodiments, the compass applications, the magnetic swipecard applications, and the other magnetic card applications may be thirdparty applications included within the third party application 842.

The applications 820 may utilize built in operating system functions(e.g., kernel 828, services 830 and/or drivers 832), libraries (e.g.,system 834, APIs 836, and other libraries 838), frameworks/middleware818 to create user interfaces to interact with users of the system.Alternatively, or additionally, in some systems interactions with a usermay occur through a presentation layer, such as presentation layer 844.In these systems, the application/module “logic” can be separated fromthe aspects of the application/module that interact with a user.

Some software architectures utilize virtual machines. In the example ofFIG. 8, this is illustrated by virtual machine 848. A virtual machinecreates a software environment where applications/modules can execute asif they were executing on a hardware machine (such as the machine ofFIG. 9, for example). A virtual machine is hosted by a host operatingsystem (operating system 814 in FIG. 9) and typically, although notalways, has a virtual machine monitor 846, which manages the operationof the virtual machine as well as the interface with the host operatingsystem (i.e., operating system 814). A software architecture executeswithin the virtual machine such as an operating system 850, libraries852, frameworks/middleware 854, applications 856 and/or presentationlayer 858. These layers of software architecture executing within thevirtual machine 848 can be the same as corresponding layers previouslydescribed or may be different.

Example Machine Architecture and Machine-Readable Medium

FIG. 9 is a block diagram illustrating components of a machine 1000,according to some example embodiments, able to read instructions from amachine-readable medium (e.g., a machine-readable storage medium) andperform any one or more of the methodologies discussed herein.Specifically, FIG. 9 shows a diagrammatic representation of the machine1000 in the example form of a computer system, within which instructions1016 (e.g., software, a program, an application, an applet, an app, orother executable code) for causing the machine 1000 to perform any oneor more of the methodologies discussed herein may be executed. Forexample the instructions may cause the machine to execute the flowdiagrams of FIGS. 5-6. The instructions transform the general,non-programmed machine into a particular machine programmed to carry outthe described and illustrated functions in the manner described. Inalternative embodiments, the machine 1000 operates as a standalonedevice or may be coupled (e.g., networked) to other machines. In anetworked deployment, the machine 1000 may operate in the capacity of aserver machine or a client machine in a server-client networkenvironment, or as a peer machine in a peer-to-peer (or distributed)network environment. The machine 1000 may comprise, but not be limitedto, a server computer, a client computer, a personal computer (PC), atablet computer, a laptop computer, a netbook, a cellular telephone, asmart phone, a mobile device, a wearable device (e.g., a smart watch), asmart home device (e.g., a smart appliance), other smart devices, a webappliance, or any machine capable of executing the instructions 1016,sequentially or otherwise, that specify actions to be taken by machine1000. In various embodiments, the mobile device refers to one or more ofthe devices described above that is considered mobile. Further, whileonly a single machine 1000 is illustrated, the term “machine” shall alsobe taken to include a collection of machines 1000 that individually orjointly execute the instructions 1016 to perform any one or more of themethodologies discussed herein.

The machine 1000 may include processors 1010, memory 1030, and I/Ocomponents 1050, which may be configured to communicate with each othersuch as via a bus 1002. In an example embodiment, the processors 1010(e.g., a Central Processing Unit (CPU), a Reduced instruction SetComputing (RISC) processor, a Complex Instruction Set Computing (CISC)processor, a Graphics Processing Unit (GPU), a Digital Signal Processor(IMP), an Application Specific Integrated Circuit (ASIC), aRadio-Frequency Integrated Circuit (RFIC), another processor, or anysuitable combination thereof) may include, for example, processor 1012and processor 1014 that may execute instructions 1016. The term“processor” is intended to include multi-core processor that maycomprise two or more independent processors (sometimes referred to as“cores”) that may execute instructions contemporaneously. Although FIG.9 shows multiple processors, the machine 1000 may include a singleprocessor with a single core, a single processor with multiple cores(e.g., a multi-core process), multiple processors with a single core,multiple processors with multiples cores, or any combination thereof.

The memory/storage 1030 may include a memory 1032, such as a mainmemory, or other memory storage, and a storage unit 1036, bothaccessible to the processors 1010 such as via the bus 1002. The storageunit 1036 and memory 1032 store the instructions 1016 embodying any oneor more of the methodologies or functions described herein. Theinstructions 1016 may also reside, completely or partially, within thememory 1032, within the storage unit 1036, within at least one of theprocessors 1010 (e.g., within the processor's cache memory), or anysuitable combination thereof, during execution thereof by the machine1000. Accordingly, the memory 1032, the storage unit 1036, and thememory of processors 1010 are examples of machine-readable media.

As used herein, “machine-readable medium” means a device able to storeinstructions and data temporarily or permanently and may include, but isnot be limited to, random-access memory (RAM), read-only memory (ROM),buffer memory, flash memory, optical media, magnetic media, cachememory, other types of storage (e.g., Erasable Programmable Read-OnlyMemory (EEPROM)) and/or any suitable combination thereof. The term“machine-readable medium” should be taken to include a single medium ormultiple media (e.g., a centralized or distributed database, orassociated caches and servers) able to store instructions 1016. The term“machine-readable medium” shall also be taken to include any medium, orcombination of multiple media, that is capable of storing instructions(e.g., instructions 1016) for execution by a machine (e.g., machine1000), such that the instructions, when executed by one or moreprocessors of the machine 1000 (e.g., processors 1010), cause themachine 1000 to perform any one or more of the methodologies describedherein. Accordingly, a “machine-readable medium” refers to a singlestorage apparatus or device, as well as “cloud-based” storage systems orstorage networks that include multiple storage apparatus or devices. Theterm “machine-readable medium” excludes signals per se.

The I/O components 1050 may include a wide variety of components toreceive input, provide output, produce output, transmit information,exchange information, capture measurements, and so on. The specific I/Ocomponents 1050 that are included in a particular machine will depend onthe type of machine. For example, portable machines such as mobilephones will likely include a touch input device or other such inputmechanisms, while a headless server machine will likely not include sucha touch input device. It will be appreciated that the I/O components1050 may include many other components that are not shown in FIG. 9. TheI/O components 1050 are grouped according to functionality merely forsimplifying the following discussion and the grouping is in no waylimiting. In various example embodiments, the I/O components 1050 mayinclude output components 1052 and input components 1054. The outputcomponents 1052 may include visual components (e.g., a display such as aplasma display panel (PDP), a light emitting diode (LED) display, aliquid crystal display (LCD), a projector, or a cathode ray tube (CRT)),acoustic components (e.g., speakers), haptic components (e.g., avibratory motor, resistance mechanisms), other signal generators, and soforth. The input components 1054 may include alphanumeric inputcomponents (e.g., a keyboard, a touch screen configured to receivealphanumeric input, a photo-optical keyboard, or other alphanumericinput components), point based input components (e.g., a mouse, atouchpad, a trackball, a joystick, a motion sensor, or other pointinginstrument), tactile input components (e.g., a physical button, a touchscreen that provides location and/or force of touches or touch gestures,or other tactile input components), audio input components (e.g., amicrophone), and the like.

In further example embodiments, the I/O components 1050 may includebiometric components 1056, motion components 1058, environmentalcomponents 1060, or position components 1062 among a wide array of othercomponents. For example, the biometric components 1056 may includecomponents to detect expressions (e.g., hand expressions, facialexpressions, vocal expressions, body gestures, or eye tracking), measurebiosignals (e.g., blood pressure, heart rate, body temperature,perspiration, or brain waves), identify a person (e.g., voiceidentification, retinal identification, facial identification,fingerprint identification, or electroencephalogram basedidentification), and the like. The motion components 1058 may includeacceleration sensor components (e.g., accelerometer), gravitation sensorcomponents, rotation sensor components (e.g., gyroscope), and so forth.The environmental components 1060 may include, for example, illuminationsensor components (e.g., photometer), temperature sensor components(e.g., one or more thermometer that detect ambient temperature),humidity sensor components, pressure sensor components (e.g.,barometer), acoustic sensor components (e.g., one or more microphonesthat detect background noise), proximity sensor components (e.g.,infrared sensors that detect nearby objects), gas sensors (e.g., gasdetection sensors to detection concentrations of hazardous gases forsafety or to measure pollutants in the atmosphere), or other componentsthat may provide indications, measurements, or signals corresponding toa surrounding physical environment. The position components 1062 mayinclude location sensor components (e.g., a Global Position System (GPS)receiver component), altitude sensor components (e.g., altimeters orbarometers that detect air pressure from which altitude may be derived),orientation sensor components (e.g., magnetometers), and the like.

Communication may be implemented using a wide variety of technologies.The I/O components 1050 may include communication components 1064operable to couple the machine 1000 to a network 104 or devices 1070 viacoupling 1082 and coupling 1072 respectively. For example, thecommunication components 1064 may include a network interface componentor other suitable device to interface with the network 104. In furtherexamples, communication components 1064 may include wired communicationcomponents, wireless communication components, cellular communicationcomponents, Near Field Communication (NFC) components, Bluetooth®components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and othercommunication components to provide communication via other modalities.The devices 1070 may be another machine or any of a wide variety ofperipheral devices (e.g., a peripheral device coupled via a UniversalSerial Bus (USB)).

Moreover, the communication components 1064 may detect identifiers orinclude components operable to detect identifiers. For example, thecommunication components 1064 may include Radio Frequency Identification(RFID) tag reader components, NFC smart tag detection components,optical reader components (e.g., an optical sensor to detectone-dimensional bar codes such as Universal Product Code (UPC) bar code,multi-dimensional bar codes such as Quick Response (QR) code, Azteccode, Data Matrix, Dataglyph, MaxiCode, PDF417, Ultra Code, UCC RSS-2Dbar code, and other optical codes), or acoustic detection components(e.g., microphones to identify tagged audio signals). In addition, avariety of information may be derived via the communication components1064, such as, location via Internet Protocol (IP) geo-location,location via Wi-Fi® signal triangulation, location via detecting a NFCbeacon signal that may indicate a particular location, and so forth.

Transmission Medium

In various example embodiments, one or more portions of the network 104may be an ad hoc network, an intranet, an extranet, a virtual privatenetwork (VPN), a local area network (LAN), a wireless LAN (WLAN), a widearea network (WAN), a wireless WAN (WWAN), a metropolitan area network(MAN), the Internet, a portion of the Internet, a portion of the PublicSwitched Telephone Network (PSTN), a plain old telephone service (POTS)network, a cellular telephone network, a wireless network, a Wi-Fi®network, another type of network, or a combination of two or more suchnetworks. For example, the network 104 or a portion of the network 104may include a wireless or cellular network and the coupling 1082 may bea Code Division Multiple Access (CDMA) connection, a Global System forMobile communications (GSM) connection, or other type of cellular orwireless coupling. In this example, the coupling 1082 may implement anyof a variety of types of data transfer technology, such as SingleCarrier Radio Transmission Technology (1×RTT), Evolution-Data Optimized(EVDO) technology, General Packet Radio Service (GPRS) technology,Enhanced Data rates for GSM Evolution (EDGE) technology, thirdGeneration Partnership Project (3GPP) including 3G, fourth generationwireless (4G) networks, Universal Mobile Telecommunications System(UMTS), High Speed Packet Access (HSPA), Worldwide Interoperability forMicrowave Access (WiMAX), Long Term Evolution (LTE) standard, othersdefined by various standard setting organizations, other long rangeprotocols, or other data transfer technology.

The instructions 1016 may be transmitted or received over the network104 using a transmission medium via a network interface device (e.g., anetwork interface component included in the communication components1064) and utilizing any one of a number of well-known transfer protocols(e.g., hypertext transfer protocol (HTTP)). Similarly, the instructions1016 may be transmitted or received using a transmission medium via thecoupling 1072 (e.g., a peer-to-peer coupling) to devices 1070. The term“transmission medium” shall be taken to include any intangible mediumthat is capable of storing, encoding, or carrying instructions 1016 forexecution by the machine 1000, and includes digital or analogcommunications signals or other intangible medium to facilitatecommunication of such software.

Language

Throughout this specification, plural instances may implementcomponents, operations, or structures described as a single instance.Although individual operations of one or more methods are illustratedand described as separate operations, one or more of the individualoperations may be performed concurrently, and nothing requires that theoperations be performed in the order illustrated. Structures andfunctionality presented as separate components in example configurationsmay be implemented as a combined structure or component. Similarly,structures and functionality presented as a single component may beimplemented as separate components. These and other variations,modifications, additions, and improvements fall within the scope of thesubject matter herein.

Although an overview of the inventive subject matter has been describedwith reference to specific example embodiments, various modificationsand changes may be made to these embodiments without departing from thebroader scope of embodiments of the present disclosure. Such embodimentsof the inventive subject matter may be referred to herein, individuallyor collectively, by the term “invention” merely for convenience andwithout intending to voluntarily limit the scope of this application toany single disclosure or inventive concept if more than one is, in fact,disclosed.

The embodiments illustrated herein are described in sufficient detail toenable those skilled in the art to practice the teachings disclosed.Other embodiments may be used and derived therefrom, such thatstructural and logical substitutions and changes may be made withoutdeparting from the scope of this disclosure. The Detailed Description,therefore, is not to be taken in a limiting sense, and the scope ofvarious embodiments is defined only by the appended claims, along withthe frill range of equivalents to which such claims are entitled.

As used herein, the term “or” may be construed in either an inclusive orexclusive sense. Moreover, plural instances may be provided forresources, operations, or structures described herein as a singleinstance. Additionally, boundaries between various resources,operations, modules, engines, and data stores are somewhat arbitrary,and particular operations are illustrated in a context of specificillustrative configurations. Other allocations of functionality areenvisioned and may fall within a scope of various embodiments of thepresent disclosure. In general, structures and functionality presentedas separate resources in the example configurations may be implementedas a combined structure or resource. Similarly, structures andfunctionality presented as a single resource may be implemented asseparate resources. These and other variations, modifications,additions, and improvements fall within a scope of embodiments of thepresent disclosure as represented by the appended claims. Thespecification and drawings are, accordingly, to be regarded in anillustrative rather than a restrictive sense.

What is claimed is:
 1. A mobile device, comprising: a housing having anintegrated surface for swiping a magnetic swipe card; a magnetometerpositioned within the housing to produce digital magnetometer outputsignals, the digital magnetometer output signals representing magneticinformation derived from the magnetic swipe card and from the Earth'smagnetic fields, each of the digital magnetometer output signals havinga magnitude related to the strength of the detected magnetic fields; amemory device for storing instructions; and a processor coupled to themagnetometer, when executing the instructions, causes the mobile deviceto: provide the digital magnetometer output signals representing themagnetic information derived from the magnetic swipe card to a magneticswipe card application for processing.
 2. The mobile device of claim 1,wherein the magnetometer comprises a 3-axis electronic compassintegrated circuit (IC).
 3. The mobile device of claim 1, wherein theprocessor, when executing the instructions, further causes the mobiledevice to: filter the digital magnetometer output signals based on themagnitude of the digital magnetometer output signals.
 4. The mobiledevice of claim 3, further comprising other magnetic components,included and within the housing; and wherein the processor, whenexecuting the instructions, further causes the mobile device to:calculate magnetic deviation caused by the other magnetic components;and adjust the digital magnetometer output signals based on thecalculated the magnetic deviation components prior to executing theinstructions that causes the mobile device to filter the digitalmagnetometer output signals based on the magnitude of the digitalmagnetometer output signals.
 5. The mobile device of claim 1, whereinthe processor executes instructions to determine at least some of thedigital magnetometer signals represent the magnetic information derivedfrom the magnetic swipe card, and further causes the mobile device to:filter the digital magnetometer output signals based on the magnitude ofthe digital magnetometer output signals related to a range of thedetected magnetic field strengths read from the magnetic information. 6.The mobile device of claim 1, wherein the processor executes theinstructions to determine at least some of the digital magnetometeroutput signals represent the magnetic information derived from theEarth's magnetic fields, and further causes the mobile device to: filterthe digital magnetometer output signals based on the magnitude of thedigital magnetometer output signals related to a range of the magneticfields strengths associated with the Earth, the range represents atleast 20,000 to 80,000 nanoteslas (nTs).
 7. The mobile device of claim1, wherein the digital magnetometer output signals includes selectabledata output signals for each of three axis magnetic components.
 8. Themobiles device of claim 1, wherein the compass application represents anavigation application.
 9. The mobile device of claim 1, wherein thedigital magnetometer output signals represents magnetic informationderived from medical information; and wherein the processor, whenexecuting the instructions further causes the mobile device to:determine at least some of the digital magnetometer output signalsrepresent magnetic information derived from the medical information; andprovide the digital magnetometer output signals representing magneticinformation derived from the medical information to another applicationfor processing.
 10. A method, comprising: generating, by themagnetometer within the mobile device, digital magnetometer outputsignals, the digital magnetometer output signals representing magneticinformation derived from the magnetic swipe card and from the othermagnetic source, each of the digital magnetometer output signals havinga magnitude related to the strength of the detected magnetic fields;executing, by a processor of a machine, at least one of a magnetic cardapplication utilizing the digital magnetometer output signalsrepresenting the detected magnetic information derived from the magneticswipe card and another application utilizing the digital magnetometeroutput signals representing the detected magnetic information derivedthe other magnetic source.
 11. The method of claim 10, furthercomprising: storing the digital magnetometer output signals; accessing,by the processor of the machine, the digital magnetometer output signalsrepresenting the detected magnetic information derived from the magneticswipe card based on instructions from the magnetic card application; andaccessing, by the processor of the machine, the digital magnetometeroutput signals representing the detected magnetic information derivedthe other magnetic source based on the other application.
 12. The methodof claim 10, wherein at least some of the digital magnetometer outputsignals represent the detected magnetic information derived from themagnetic swipe card further comprises: filtering the digitalmagnetometer output signals based on the magnitude of the digitalmagnetometer output signals.
 13. The method of claim 10, furthercomprising: determining least some of the digital magnetometer outputsignals represent the magnetic information derived from the magneticcard information, including: filtering the digital magnetometer outputsignals based on the magnitude of the digital magnetometer outputsignals related to a range of the detected magnetic field strengths readfrom the magnetic information.
 14. The method of claim 10, furthercomprising: determining at least some of the digital magnetometer outputsignals represent the detected magnetic information from the othermagnetic source, including: filtering the digital magnetometer outputsignals based on the magnitude of the digital magnetometer outputsignals related to a range of the magnetic fields strengths associatedwith the Earth, the range represents at least 20,000 to 80,000nanoteslas (nTs).
 15. The method of claim 10, further comprising:determining at least some of the digital magnetometer output signalsrepresent magnetic information derived from medical information; andproviding the digital magnetometer output signals representing magneticinformation derived from the medical information to a medicalapplication for processing.
 16. The method of claim 15, whereindetermining at least some of the digital magnetometer output signalsrepresent magnetic information derived from medical information furthercomprises: determining at least some of the digital magnetometer outputsignals represent magnetic information derived from blood samples.
 17. Anon-transitory machine-readable storage medium in communication with atleast one processor, the machine-readable storage medium storinginstructions which, when executed by the at least one processor,performs operations comprising: generating, by the magnetometer withinthe mobile device, digital magnetometer output signals, the digitalmagnetometer output signals representing magnetic information derivedfrom the magnetic swipe card and from the other magnetic source, each ofthe digital magnetometer output signals having a magnitude related tothe strength of the detected magnetic fields; executing, by a processorof a machine, at least one of a magnetic card application utilizing thedigital magnetometer output signals representing the detected magneticinformation derived from the magnetic swipe card and another applicationutilizing the digital magnetometer output signals representing thedetected magnetic information derived the other magnetic source.
 18. Thenon-transitory machine-readable storage medium of claim 17, theoperations further comprising: storing the digital magnetometer outputsignals; accessing, by the processor of the machine, the digitalmagnetometer output signals representing the detected magneticinformation derived from the magnetic swipe card based on instructionsfrom the magnetic card application; and accessing, by the processor ofthe machine, the digital magnetometer output signals representing thedetected magnetic information derived the other magnetic source based onthe other application.
 19. The non-transitory machine-readable storagemedium of claim 17, wherein at least some of the digital magnetometeroutput signals represent the detected magnetic information derived fromthe magnetic swipe card further comprises: filtering the digitalmagnetometer output signals based on the magnitude of the digitalmagnetometer output signals.
 20. The non-transitory machine-readablestorage medium of claim 17, the operations further comprising:determining least some of the digital magnetometer output signalsrepresent the magnetic information derived from the magnetic cardinformation, including: filtering the digital magnetometer outputsignals based on the magnitude of the digital magnetometer outputsignals related to a range of the detected magnetic field strengths readfrom the magnetic information.